You will do demonstrations of your working project at the end several Sprints. These demos will prepared by your team in advance and either be given during class time to an audience (possibly your instructor, student course assistant(s) or peers) and/or previously pre-recorded.
Your instructor may have you use the team/breakoutrooms or stay in the
classroom (and/or have the team record the demos and submit mp4 files to myCourses as well as a link to the video uploaded to youtube - check with your instructor!). Given the number of teams in your section and
availability of a course assistant, you must plan on the length of your demo to be only between10-12 minutes to
demonstrate your project implementation and allow for questions. All teammates are expected to participate.
While grading your sprint
submission, your instructor will also run the application to test its
functionality.
We cannot stress this enough, get clarification from your instructor/client in advance so you know exactly what is expected from your team and you are not scrambling to prepare or violating the time allotment.
You will use your acceptance
test plan to drive the demos, so the team must ensure that it is
up-to-date for the sprint submission, and clearly indicates the user
stories that were implemented in each sprint and the acceptance
criteria for each story. The following provides information about what
will be expected for each demo.
Sprint 1 Demonstration - Elaboration
Phase User Stories
The Sprint 1 demo will show the implementation of the user
stories specified in your project starter Trello planning board. This
is a small number of stories and acceptance criteria so you should be
able to show all of the implemented functionality in the alloted time. Be aware that extra work will not be penalized but what is required should be working without glitch and is clearly stated through the acceptance criteria given to you.
This demonstration will have a lot of functionality to show. It
will be all of the minimum viable product (MVP). Since the time may be as short as
12 minutes, you most likely will have to setup in advance multiple
demonstration scenarios running on more than one machine to be able to
show all of the features in the time allocated.
Sprint 3 Demonstration - MVP and
Enhancement User Stories
This demonstration will have a lot of functionality to show. It
will be all of the minimum viable product (MVP) and the bugfree
enhancements that you implemented. Once again, since the time may be as short as
12 minutes, you most likely will have to setup in advance multiple
demonstration scenarios running on more than one machine to be able to
show all of the features in the time allocated.
